
idea:
    'idea' is a repo to share project ideas and projects based on those shared
    ideas, sometimes one might come up with good iead for something and want to
    share it but not necessary implement/create it all or at all themselfs, this
    approach gives a single place for all those ideas
    

legal consideration:
    I'm not a lawyer so can't tell if this is bidig or not but
    here's my take, I wanted something that woud allow me to keep
    as much of 'ownership' of those ideas as I can, so instead of
    licenses I thought of this:
    '''
    there is NO LICENSE, if you are interested
    and/or have any suggestion for any of the ideas
    or already started projects, contact me directly
    (feel free to share link to this repository anywhere)
    '''
    of course you can put any license you want, also
    if you want to open any of the ideas you shoud add
    appropriate information somewere, like adding license
    file inside any folder containing ideas you want to open
    

readme example:
    '''
    # idea


    #### ideas with resources for various projects
    each folder is separate project idea

        there is NO LICENSE, if you are interested
        and/or have any suggestion for any of the ideas
        or already started projects, contact me directly
        (feel free to share link to this repository anywhere)

        
    #### ideas/project with some relevant info:
    information about scope of license at the end
    ~~~sh
    idea:
        description: single place to share ideas and projects based off them
        license    : MIT
    ~~~
    ~~~sh
    foo:
        description: place for all of your foos, bars and bazs
        home page  : http://projectofoo.com
        repo       : https//notabug.org/fil/foo
    ~~~


    #### disclaimer:
    license part is referring only to idea name containig it, and
    not to anything else, following example means that license
    to idea 'foo' is MIT and that idea 'bar' has no license
    ~~~sh
    foo:
        repo: ------
        license: MIT
    ~~~
    ~~~sh
    bar:
        repo: ------
    ~~~
    this information is only added for convience sake and is
    NOT BINDING IN ANY WAY, each idea will contain a license file
    in it's folder, THAT IS BINDING ONLY IT'S CONTAINING FOLDER, so
    double check there, if you have any doubts or questions contact me

    also the license to idea repository APPLAYS ONLY TO CONCEPT OF REPOSITORY
    CONTAINING IDEAS AND RESOURCES, NOT TO ANY RESOURCES THAT ARE CONTAINED WITHIN
    ANY INSTANCE OF IT, meaning in this(idea repo) case MIT license is binding only
    for materials within it's folder inside repository and not anywhere else perioid
    
    
    #### contact me:
        you at example.com
    '''


work flow:
    same as normal repo with addition of public remote containing
    only master branch, that needs to be 'exported' for the world
    to see, witch basically makes it much harder to push anything
    unnecessary/unwanted to public eyes by a mistake


setup:
    this assumes you work on one account also
    this setup is performed per each local clone

    setting up private remote:
        - check remote addresses
            $ git remote -v
            origin	{ssh_address_of_private_repo} (fetch)
            origin	{ssh_address_of_private_repo} (push)
        - add public repo remote
            $ git remote add public_repo {ssh_address_of_public_repo}        
        - check remote addresses
            $ git remote -v
            origin	{ssh_address_of_private_repo} (fetch)
            origin	{ssh_address_of_private_repo} (push)
            public_repo	{ssh_address_of_public_repo} (fetch)
            public_repo	{ssh_address_of_public_repo} (push)

    synchronizing public and private repo [only once on empty private repo]:
        - fetch public repo master branch
            $ git fetch public_repo master
        - do whatever it takes so that both maser brancahes are
          identical, here's quick and dirty way to archieve that
          !!! IMPORTANT: you need to be on master branch !!!
            $ git reset --hard public_repo/master
            $ git push --force

    pulling from public repo:
        fetch any changes then ff/merge/rebase them as necesarry

    pushing to public repo:
        $ git push public_repo master

